Mobile electronic device for identifying and recording an animal harvest

ABSTRACT

Systems, methods and one or more computer readable storage media are configured to facilitate entry by a user into a first electronic device of information associated with an animal harvest, where the information includes at least one of an animal species, a geographic location indicating where the animal harvest occurred, and a date of the animal harvest. Harvest data is uploaded from the first electronic device to a second electronic device, where the harvest data includes the information entered by the user.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a Continuation of U.S. patent application Ser. No. 14/939,038filed Nov. 12, 2015, which claims priority to U.S. ProvisionalApplication Ser. No. 62/108,205 filed Jan. 27, 2015, and the disclosuresof these applications are incorporated herein by reference in theirentireties.

FIELD

The present invention relates to a mobile electronic device that assistsa user in the identification and recording of a harvest of fish or othergame in fishing and hunting activities.

BACKGROUND

Hunting and fishing activities of wildlife game are popular for theoutdoor sports enthusiast. To ensure that such activities can besustainable and also are beneficial to the ecology of a particularwildlife environment, federal and/or local government laws and/orregulations are typically implemented to control how and when harvestingof wildlife animals can occur. Such laws and/or regulations include therequirement for one to obtain a hunting or fishing license for aparticular harvest season, as well as rules for controlling the numberand/or types of animals that can be harvested during this season. Forexample, local gaming authorities may obtain information on animalsharvested by requesting or requiring that information is reportedregarding wildlife animals being harvested (including informationrelating to the species of the animal, size of the animal, sex of theanimal, etc.). This allows local gaming authorities to ascertain aparticular animal population at any given time and accordingly establishharvesting rules as needed to ensure such animal population can besustained. Currently, reporting of harvesting by people engaged inwildlife gaming activities is performed by manually reporting to localauthorities (e.g., at reporting stations).

Accordingly, it would be desirable to provide a mechanism allowing awildlife sports person to record and/or report information relating to aharvest in a an easy and reliable manner.

SUMMARY

In accordance with example embodiments of the invention, one or morecomputer readable storage media are encoded with software comprisingcomputer executable instructions that, when the software is executed,are operable to facilitate entry by a user into a first electronicdevice of information associated with an animal harvest, where theinformation comprises at least one of an animal species, a geographiclocation indicating where the animal harvest occurred, and a date of theanimal harvest. The instructions are further configured to uploadharvest data from the first electronic device to a second electronicdevice, where the harvest data includes the information entered by theuser.

Systems and methods are also described herein that are configured toperform the same or similar operations as the one or more computerreadable storage media.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example embodiment of an electronic device configuredfor implementing features in accordance with the present invention.

FIG. 2 depicts a schematic box diagram of a system configured toimplement features in accordance with the present invention.

FIG. 3 depicts a flow chart of operational features for an exampleembodiment in accordance with the present invention.

FIGS. 4A-4D depict example embodiments of a graphical user interface forthe electronic device of FIG. 1 that implement certain features inaccordance with the present invention.

FIGS. 5A-5C depict example embodiments of a graphical user interface forthe electronic device of FIG. 1 that implement certain features inaccordance with the present invention.

FIG. 6 depicts an example embodiment of a graphical user interface forthe electronic device of FIG. 1 that implements certain features inaccordance with the present invention.

FIGS. 7-18 depict an example embodiment of a graphical user interfacefor the electronic device of FIG. 1 that implements features of a mobileapp for recording catches for fishing in accordance with the presentinvention.

Like reference numerals have been used to identify like elementsthroughout this disclosure.

DETAILED DESCRIPTION

As described herein, an electronic device is configured to facilitateidentification and recording of animal harvests, such as identifying andrecording the harvesting of fish or hunting of deer, fowl or other game.In example embodiments described herein, an electronic device comprisesa mobile device configured with one or more software applications, alsoreferred to herein as mobile applications or mobile apps, that provide asuitable user interface for user interaction with the mobile device tofacilitate entry of information by the user to identify a species of aharvested animal and record a location, time and specific features ofthe harvested animal for entry at a database that is accessible by otherusers. As used herein, the term “harvest” refers to capture and/orkilling of an animal for human use (e.g., capture and release of ananimal, or capture and kill of an animal for human use and/orconsumption). The example embodiments described herein are in relationto harvesting of fish. However, the invention is also applicable toharvesting of a variety of different animal species including, withoutlimitation, fish, deer, bear, turkeys or other fowl and/or any othertypes of wildlife game sanctioned for harvest.

An example embodiment of a mobile device 2 implemented for operation inaccordance with the present invention is depicted in FIG. 1 andcomprises a mobile phone or smart phone. The mobile device 2 includes adisplay 4 and a series of icons or tiles 6 displayed that representsoftware applications or mobile apps for the phone 2.

A schematic block diagram is depicted in FIG. 2 of an environment or asystem in which the mobile device 2 communicates with other electronicdevices, such as a server 20 that receives and stores harvestinginformation provided by users via mobile devices 2 and/or other types ofelectronic devices as described herein. In particular, communicationsand exchange of information between electronic devices is facilitatedvia any suitable one or more networks (represented by the double arrowlinking mobile device 2 with server 20). Examples of types of networksthat can be utilized to facilitate communications and exchange ofinformation between two or more electronic devices include, withoutlimitation, any one or more of local or wide area networks, InternetProtocol (IP) networks such as intranet or internet networks, telephonenetworks (e.g., public switched telephone networks), wireless or mobilephone or cellular networks, and any suitable combinations thereof. It isto be understood and appreciated that, while FIG. 2 only shows mobiledevice 2 in communication with server 20, the network(s) facilitatecommunications with any selected number of electronic devices (e.g.,hundreds, thousands or more computing devices).

In addition to the display 4, the mobile device 2 includes a processor8, a network interface 9, and memory 5. Similarly, the server 20includes a processor 22, a network interface 23, and memory 24. Each ofthe mobile device 2 and server 20 can further be integrated with otherdevices and/or include any suitable types of peripheral devices that canbe connected to the devices to facilitate input of audio, video or otherinformation by a user to the computing device (e.g., keyboards, mousedevices, cameras, microphones, etc.) as well as presentation (output ordisplay) of audio, video and/or other types of information to the userby the devices.

The network interfaces 9 and 23 can be, for example, one or more of anEthernet interface card or switch, a modem, a router or any othersuitable hardware device that facilitates a wireless and/or hardwireconnection over the network(s), where the network interface unit can beintegrated within the device (e.g., for the mobile device 2) or aperipheral that connects with the device (e.g., for the server or anyother electronic device in communication with other electronic devicesvia the network(s)).

Each of the processors 8, 22 can comprise a microprocessor that executescontrol process logic instructions 12, 26 stored within memory 5, 24,including operational instructions and software applications storedwithin such memory, such as the mobile apps 6 stored within the memory 5of the mobile device 2 or that software application(s) 28 stored withinmemory 24 of the server 20. The processors 8 and 22 perform operationsin accordance with the steps set forth in the flow chart of FIG. 3 andutilizing the harvest monitor app 16 and harvest monitor software 28 ofmemories 5 and 24.

The memories 5 and 24 of the mobile device 2 and server 20,respectively, comprise one or more computer readable storage media thatmay further comprise read only memory (ROM), random access memory (RAM),magnetic disk storage media devices, optical storage media devices,flash memory devices, electrical, optical and/or other physical/tangible(e.g., non-transitory) memory storage devices, and any combinationsthereof. In other words, the one or more computer readable storage mediaare one or more physical, tangible hardware devices that that can retainand store instructions for use by an electronic device (e.g., a mobilephone or other computer device that incorporates some or all of the oneor more computer readable storage media), for example including softwarecomprising computer executable instructions operable to perform certainoperations when the software is executed. A computer readable storagemedium (or one or more computer readable storage media), as used herein,is not to be construed as being transitory signals per se, such as radiowaves or other freely propagating electromagnetic waves, electromagneticwaves propagating through a waveguide or other transmission media (e.g.,light pulses passing through a fiber-optic cable), or electrical signalstransmitted through a wire.

The display 4 of the mobile device 2 can be an LCD or any other suitabletype of display, including a touch pad display for display of textualand/or graphical content by the processor, including audio, video,textual, interactive and/or any other forms of content which may beoperated and controlled by a user utilizing a mobile app 6 such as theharvest monitor app 16.

The mobile device 2 and/or other electronic devices, including server20, can utilize any suitable operating system (OS) to enable operationsof the devices including, without limitation OS platforms commerciallyavailable under the trademarks or tradenames Microsoft Windows(Microsoft Corporation), OS X (Apple), iOS (Apple Inc.), Linux, Android(Google Inc.), etc. Example embodiments of a mobile device 2 that can beimplemented to utilize the harvest monitor app 16 within memory 5 toperform operations in accordance with the present invention include,without limitation, smart phones commercially available under thetrademarks or tradenames Apple iPhones (Apple, Inc.), Samsung Galaxy(Samsung Corporation), Xperia (Sony Corporation) and LG (LGCorporation). However, as previously noted, harvest monitor applicationsof the present invention can also be implemented with any other suitableelectronic/computing device including, without limitation, personalcomputers such as desktop computers, laptops, tablets and/or any othertypes of computing devices implementing any of the previously noted OSplatforms to facilitate performing operations in accordance with thepresent invention. Further, it is noted that the server 20 depicted inFIG. 2 can be implemented as a single server or any number of serverdevices.

The harvest monitor app 16, harvest monitor software 28, and/or anyother types or forms of suitable software utilized to perform harvestrecording operations in accordance with the present invention can beobtained in any suitable manner. For example, the harvest monitor app 16can be downloaded from the server 20 and/or any other suitable computingdevice for storage and use by the mobile device 2 as well as otherelectronic devices.

Operation of the mobile device 2 within the system for identifying andrecording an animal harvest is described with reference to the flowchartof FIG. 3. A user, such as a fisherman, implements the operations of thepresent invention by initially opening or enabling the harvest monitorapp 16 on the mobile device 2 (e.g., by clicking on an icon on thedisplay 4 representing the app 16). When implemented, the harvestmonitor app 16 provides a user interface (e.g., refer to FIGS. 4-6) thatallows the user to enter information about the harvest as well as obtaininformation regarding the harvest via the app 16.

When a fish is caught by the user and the user desires (or is required)to record the harvest (e.g., catch and release, or catch and keep), ageographic location of the harvest is initially determined at 100. Ageographic reference code (GRC) can represent, e.g., a body of water,county, or territory in which the harvest was made. A GRC can beassigned, e.g., by a designated federal, state and/or local governmentalbody or authority that manages and governs harvest records for regulatedfish and/or game animals. Alternatively, the GRC can be assigned by aprivate entity that hosts a website and/or a software platform thatcollects harvest data for mobile and/or other electronic devices. In anexample embodiment, a GRC can be obtained through publicly availableinformation, such as web based and/or other types of publicationsprovided by the federal/state/local regulatory authority for thegeographic region (see, e.g.,http://www.dfw.state.or.us/resources/licenses_regs/docs/fishing_harvest_card_location_codes.pdf,which is a website publication by the state of Oregon relating toharvest location codes for particular areas in which fish or other gameis harvest). GRC information can be downloaded by the mobile device 2for use as needed and/or for storage by the device for use by the app16.

The harvest monitor app 16 can download GRCs for the mobile device 2(e.g., from the server 20 and/or from other sources available over theInternet or other networks). The app 16 can either obtain a specificgeographic location from manual entry by the user (e.g., the user entersa specific area or region and/or the GRC region in which the harvest wasmade, such as manual entry of the name of a site, park, lake or otherarea, the particular mile marker on a specific trail, etc.) orautomatically using GPS (global positioning system) software. Forexample, the mobile device 2 can utilize conventional and/or any othertypes of suitable GPS software to obtain specific GPS coordinatesidentifying a global position of the mobile device 2, and suchinformation can be utilized by the app 16 (e.g., in combination with GRCinformation available for use by the app 16) to automatically obtain theGRC. In an example embodiment depicted in FIGS. 4A-4C, a graphical userinterface (GUI) 40 for the harvest monitor app 16 displayed by thedisplay 4 of the mobile device 2 provides an option for the user toallow the app 16 to access the user location so as to automaticallyobtain the GRC. When the user enables the app 16 to perform thisoperation (by selecting “ALLOW” in the pop-up menu option 50 displayedon GUI 40 in FIG. 4A), the app 16 performs operations (e.g., utilizingGPS location software) to obtain the location of the mobile device 2 andconvert such location information to a GRC value. As shown in FIG. 4C,the app 16 automatically obtains the GRC value of 185 (e.g.,representing an area of the Willamette River and Slough below OregonCity Falls in Oregon).

In example embodiments, the harvest monitor app 16 can further beconfigured to automatically obtain additional information (e.g., fromthe server 20) associated with the GRC that may be of interest to theuser of the mobile device 2. For example, a federal, state and/or localgovernmental body or authority that manages and governs harvest recordsfor regulated fish and/or game animals in a particular GRC region mayprovide time sensitive alert messages relating to hunting and/or fishingrestrictions or allowances in the GRC region, and such messages can bedownloaded by the harvest monitor app 16 for display by the mobiledevice 2. For example, in a scenario in which recorded harvesting of oneor more different types of fish in a particular GRC region and over acertain time period is large enough that there is a concern forover-harvesting, an alert message may be provided that establishes alimit or a restriction on harvesting of the type(s) of fish in that GRCregion for a select time period.

A specific example scenario of an alert message for a GRC region thatmay be provided by the harvest monitor app 16 for display by the mobiledevice 2, when that specific GRC region has been identified as describedherein, can be “this zone is closed for fishing from Aug. 1, 2015through Oct. 1, 2015”. In another example embodiment for a specific typeof fish, the alert message might be “A non-fin clipped fish cannot beharvested in this zone as of 8/1. Notification of allowance ofharvesting of non-fin clipped fish in this zone will be indicated at afuture date.” A still further example of an alert message is “As of Nov.1, 2014, a non-fin clipped fish may be harvested in this zone.” Thealert notice can be provided in any suitable format as a display messageand during any time in which the harvest monitor app 16 is enabled and aGRC region of interest has been identified. An example embodiment of analert message 54 (a fictitious message provided by the state ofWashington Department of Fish and Wildlife—WDFW) for an identified GRCregion (displayed in the GUI 40 as Forks, Wash.) provided to the displayof the mobile device 2 via the harvest monitor app 16 is depicted inFIG. 4D. The harvest monitor app 16, via the GUI 40, can also allow theuser to access further information about the alert message 54 (e.g., byproviding a link to the site of the governmental body or authority thatmanages and governs harvest records for regulated fish and/or gameanimals in the GRC region, or obtaining additional information about thealert from the server 20 for display via the GUI 40).

At 110, an animal type and/or species is established. The animal type orspecies can also be obtained via public record information, images,drawings and/or historical reference information that is available tothe user and/or via the harvest monitor app 16. For example, the usermay know the particular species of a fish that is caught. Alternatively,the user may utilize the app 16 and/or other apps of the mobile device 2to assist in identifying the fish species (e.g., by viewing photographs,drawings and/or other information displayed by the mobile device formaking a determination regarding the species of fish caught). Someexamples of fish species that may be harvested in a particular GRCregion include, without limitation, Chinook Salmon, Coho salmon,Steelhead, Sturgeon, Halibut, clams, crab, etc. Entry of informationregarding the animal species (as well as other types of information tobe provided by the user) may be enabled, utilizing the GUI 40, via apull-down menu (where different animals and/or animal species areavailable in the pull-down menu for selection by the user), via entry oftext within user-fillable fields of the GUI 40, etc.

In another example embodiment, the app 16 can facilitate an automaticidentification from a photograph of the species of fish caught by theuser. For example, the user can capture and save a photographic(digital) image of the fish (or other animal) that has been caughtutilizing a built-in camera of the mobile device 2, and this capturedimage can be utilized by the app 16 to automatically identify or suggesta species of the fish (e.g., based upon image recognition softwareassociated with the app 16 that identifies elements of the fish andcompares such identified elements with a catalog or library of images ofknown fish species in order to provide recommendations to the useridentifying the caught fish). Alternatively, the app 16 can provide thephotographic (digital) image captured by the mobile device 2 as part ofthe harvest data to be uploaded to the server 20 and/or saved by themobile device 2 in relation to the specific harvest record.

Upon establishing the animal species, a designated animal code isestablished at 120. Animal codes can be assigned, e.g., by thedesignated federal, state and/or local governmental body or authoritythat manages and governs harvest records for regulated fish and/or gameanimals in the GRC region. Alternatively, animal codes can be assignedby a private entity hosting the server 20 that collects harvest datarecords. Animal codes can be obtained through public informationincluding, without limitation, public website information that may bedownloaded as needed and/or stored by the mobile device 2 for use by theapp 16. An example embodiment of animal codes for fish species isprovided in the following table:

Codes Species of Fish 1 Chinook Fin-Clipped (Hatchery) (king orblackmouth) - has black lower gum line 1W Chinook Unmarked (Wild) (kingor blackmouth) - has black lower gum line 2 Coho Fin-Clipped (Hatchery)(silver) - has white lower gum line 2W Coho Unmarked (Wild) (silver) -has white lower gum line 3 Other Salmon - Pink (humpy); Chum (dog); orSockeye

The animal code can be manually entered at the GUI 40 or automaticallyprovided by the harvest monitor app 16 (e.g., based upon an automaticidentification of the animal species or in response to the user manuallyentering the animal species name via the GUI 40). In an exampleembodiment, the GUI 40 provides a listing, such as a pull-down menurepresenting information such as that shown in the previous table thatallows the user to select an animal species (step 110), and thisautomatically results in the animal code being established (step 120).

In an embodiment in which the user has not identified the animal speciesbut instead captures an image of the harvested animal, an animal codecan be provided for the harvest record later. For example, a harvestrecord that has not been animal coded can be flagged or marked for latercoding (e.g., providing some identified indicating the record is notcomplete). An administrator of the server 20, utilizing the capturedimage of the harvested animal and/or other information provided by theuser via the app 16, can provide the animal code to complete the harvestrecord. Alternatively, the user of the mobile device 2 can also providethe animal code at a later date.

In addition to the animal code being provided via the app 16, furtherinformation can optionally be provided by the user to the app 16 (viathe GUI 40) at 130 in relation to the harvest. For example, a federal,state and/or local regulatory authority or, alternatively, a privateentity, hosting the server 20 may require that a harvest record for aparticular animal code include information such as time/date of harvest,status of harvest (e.g., catch and release or catch and keep), animalsize (e.g., animal length and/or weight), animal sex, specific featuresand/or markings of animal (e.g., colors, hatchery and/or radio frequencytagmarkings, injury marks and/or other features that may be unique tothe animal), etc. In an example embodiment, such additional informationfor a harvested fish species might be as follows:

Zone Fish Size Date Wild/Hatchery 185 Coho (silver) fin 32 inches Nov.1, 2012 Hatchery clipped

In this example, the zone 185 refers to the GRC region, features of thefish are that it is a Coho (silver) and has one or more fins clipped(indicating the fish is from a hatchery), the size is 32 inches, theharvest date is Nov. 1, 2012, and the fish is not wild but came from ahatchery (indicated by the one or more clipped fins). The informationcan be provided through the GUI 40 in any suitable manner (e.g., via oneor more drop-down menus, via user-fillable text fields, etc.).

At 140, the harvest information can be communicated from the mobiledevice 2 to the server 20. The server 20, utilizing harvest monitorsoftware 28, maintains harvest records for one or more different typesof animals and/or animal species. For example, the server 20 cancomprise a database hosted by a federal, state and/or local regulatoryauthority that maintains data records on harvested animals for purposesof monitoring and controlling ecological environments within the GRCregion regulated by such authority. Alternatively, the server 20 cancomprise a database hosted by a private entity that provides access toharvest information to users (e.g., subscribers to the database). Forexample, the harvest information may be of interest to users such ashunters and/or fishing enthusiasts desiring information regarding typesof animals and/or animal species that are harvested as well as frequencyof harvest of such animals/animal species in particular GRC regions.

Other information that can be communicated to the server 20 by themobile device 2 includes information about the user harvesting theanimal, such as user name and other information associated with the usersuch as user address, user phone number, etc. The user may also beprompted by the app 16 to provide license information (e.g., informationrelating to a hunting license, a fishing license or a fishing permit)that may be required by the designated federal, state and/or localgovernmental body or authority that manages and governs harvest recordsfor regulated fish and/or game animals in the GRC region in which theanimal is harvested. In an example embodiment, the user may provide hisor her hunting and/or fishing license registration and any otherinformation about the user (e.g., user name, address, phone number,etc.) in an initial (e.g., start-up) feature of the app 16 so that theapp 16 automatically provides the user's license information as part ofthe harvest data each time such data is provided to the server 20. Otherfeatures of the app 16 can include license registration and/or licenserenewal of the user via the app 16 with the designated federal, stateand/or local governmental body or authority that manages and governsharvest records for regulated fish and/or game animals in a particularGRC region.

The harvest monitor app 16 can further provide a display within the GUI40 of information entered by the user and/or automatically obtained bythe app 16 for review by the user prior to being provided forrecordation at the server 20. Any information that may be inaccurate canbe corrected by the user prior to recordation. In addition, the app 16may store the harvest data at the memory 5 of the mobile device 2 inaddition to providing such harvest data to the server 20 forrecordation. Further, the specific GPS coordinates obtained by themobile device 2 in relation to the catch of the animal can also bestored by the app 16 within the memory 5 of the mobile device 2 as wellas included as part of the harvest data for recordation by the server20. This provides a precise location of the animal catch in addition toits general harvest location provided by the GRC region.

In the event the mobile device 2 cannot establish a connection over anetwork with the server and/or other electronic devices, informationthat is stored by the mobile device 2 in relation to the harvest can beprocessed at a later time when such network connection can beestablished so as to ensure that a data record of the harvest isobtained and adequately recorded. For example, the harvest monitor app16 can monitor whether a communication of harvest data has beenestablished with the server 20 and adequately recorded. If suchcommunication has not been established, the app 16 can automaticallyestablish such connection at a time when a network connection isachieved or, alternatively, automatically notify the user that aconnection has not been established to adequately transfer harvest datato the server 20 so as to notify the user that a record of the harvestshould be communicated (either manually or via the app 16) at a latertime.

Thus, the system, comprising an electronic device, a server, and one ormore computer readable storage media including one or more softwareapplications, facilitates operations in accordance with the presentinvention that provides adequate identification and recordation ofharvest data for a harvested animal that may be required by a designatedfederal, state and/or local governmental body or authority that managesand governs harvest records for regulated fish and/or game animals inthe GRC region in which the animal is harvested. Such information canalso be made available for use by a server hosted by a private entitythat provides information to users (e.g., on a subscription basis) whodesire information regarding types and/or frequency of animals harvestedin particular GRC regions.

Further, for certain GRC regions in which the designated governmentauthority requires a tag to be recorded for a harvested animal, theharvest data stored by the harvest monitor app 16 at the mobile device 2and that is provided to a server 20 for recordation can further serve asan electronic tag for the harvested animal. The harvest data stored atthe mobile device 2 can further be displayed as evidence that theharvested animal has been tagged in the event a user encounters agovernment official (e.g., a game warden) having authority for the GRCregion.

Information utilized by the harvest monitor app 16 and/or to be providedas harvest data to a server 20 by the app 16 can be obtained/transferredby the mobile device 2 via automatic downloads/uploads (e.g., atdesignated hourly, daily, weekly or monthly time intervals) and/ormanually (e.g., by the user prompting, via the GUI 40 of the app 16, adownload of information to the mobile device 2 or an upload of harvestdata to a server 20).

Thus, the harvest data provided via the mobile device (or otherelectronic device) via suitable software of the device can be used forthe tracking of fish and game harvests for reference and use by publicor private entities. Such entities may include, without limitation,federal, state and/or local governing bodies, and private (e.g., “forprofit”) entities or educational (e.g., “not-for-profit”) entities.Private entities might gather such harvest data for marketing the datato users (e.g., subscribers) interested in such information (e.g., forhunters and/or fishing enthusiasts planning vacations, hunting/fishingtrips, for recreational or commercial harvest sporting activities,etc.). Educational entities might desire such harvest data for purposesof public education and/or research.

Other features of the harvest monitor app 16 include allowing the userto manually check a GRC to confirm that it correctly identifies theregion in which the harvest occurred (e.g., the GRC correctlycorresponds with GPS information obtained by the mobile device 2) andallow the user to report to the server 20 (or other electronic devicevia a network) that there may be an error with the GRC. The app 16 canalso be configured to enable the user to report other inaccurateinformation associated with a GRC (e.g., a referenced zone, territory orbody of water), an inaccurate animal code, etc. Verification of theharvest data can be achieved in a series of verification prompts,requests or messages provided by the app 16 utilizing the GUI 40. Whenthe final verification message has been confirmed by the user, theinformation gathered during the harvest information collection processcan be stored by the mobile device 2 and/or provided to the server 20.

In the event a network connection is not available at the current time(e.g., the user may be in a GRC zone where cellular/mobile phone serviceis spotty or unavailable), the app 16 can be configured to facilitate amanual check of the GRC or other harvest information via data alreadystored by the mobile device 2 (e.g., via a previous download of suchdata).

In an example embodiment depicted in FIGS. 5A-5C, additional informationand/or functions are enabled via the GUI 40 of the harvest monitor app16, where the user can make a selection (as depicted by the displayicons or interactive buttons 60 in FIG. 5A) to view a display of GRCs(also referred to as harvest zone numbers, displayed in the list 62 ofFIG. 5B when the user selects this function), view local regulations(e.g., current fishing regulations for the state of Oregon, provided asa PDF document 64 for display by the mobile device 2 as depicted in FIG.5C), or report inaccurate zoning information to the server 20. As partof the inaccurate zone reporting (or provided as a separate function),the GUI 40 of the app 16 can also enable the user to report theircurrent location, either as a GRC or a description of the user'slocation (e.g., utilizing functions enabled by the GUI 40 as depicted inFIG. 6). For example, the user may determine that a GRC is incorrectlyassociated with certain GPS coordinates. In the event the user hasidentified the correct GRC that should be associated with the user'sprecise location (e.g., by viewing the list 62 depicted in FIG. 5B), theuser might enter this GRC such that the correct GRC is associated withthe GPS information provided by the user's mobile device 2.

Harvest data records can be provided to a single server or to multipleservers hosted by multiple parties that provide a database of theharvest data records from the present user as well as other usersassociated with the system. The timing of harvest data uploads to aparticular server/database system can be defined by a service orlicensing agreement between the parties. The harvest data can beprovided in any suitable format that can be used by electronic devicesassociated with the system.

The following examples provide scenarios in which the system may beimplemented to benefit users in relation to the harvest data collected.

Example 1

A fisherman may have interest in knowing the most up to date locationwhere a certain type of fish is being caught. By accumulating theharvest data associated with a particular GRC region and/or specific GPSdata points associated with the harvest data, such data may be of valueto the fisherman in determining a spot or location to fish. Thisinformation provides value to customers such as fishing guides,commercial fisherman, sportsman and educational or research entities.

Example 2

Server databases can provide tiered programs or subscription rates tousers with different, more advanced features depending upon thesubscription tier. In addition, the harvest monitor software 28 of oneor more servers may be configured to provide targeted advertising tosubscribers based upon GRC locations of interest (e.g., advertising forhotels, restaurants, commercial fishing charters, etc. for a particularGRC region of interest to a particular user as indicated by harvest datadownloaded from the server 20 to the user's mobile or other electronicdevice).

For example, one or more hotels within a GRC region of interest to asubscriber (as indicated by harvest data downloads by the device of thesubscriber) may desire to provide target advertising to such subscriber.The harvest monitor app 16 and/or harvest monitor software 28 can beconfigured to facilitate such target advertising.

An example embodiment of a harvest monitor mobile app implemented foruse by a mobile device 2 is now described with reference to FIGS. 7-18.Referring to FIG. 7, a user accesses a mobile app 70 that integratesfeatures of the harvest monitor mobile app described herein withfeatures associated with a particular state's gaming regulations. Inthis scenario, the mobile app 70 integrates features of the harvestmonitor app with fishing regulations for the state of Oregon, includingfeatures of associating a state registered fishing license registrationassociated with a catch as well as obtaining and/or recordinginformation associated with one or more punch cards associated with afishing license. A punch card is obtained in association with aregistered fishing license and provides a mechanism for one to recordcatches of particular types of fish.

When a user initiates or opens the mobile app 70 on his or her mobiledevice 2, a main menu 72 as depicted in FIG. 8 can be initially beprovided that allows the user to select from a number of features,including recording a catch, display of a punch card associated with theuser's license registration, finding a GRC (harvest zone number) such asthe GRC in which the user is located (e.g., utilizing techniques asdescribed herein and with reference to FIGS. 4A-4C), obtaining statefishing regulations (e.g., ODFW or Oregon Department of Fish andWildlife fishing regulations), and the option for a user to report aninaccurate zone or GRC. As depicted in FIG. 8, a selection is made bythe user to record a catch.

At FIG. 9, a drop-down menu 74 is depicted allowing the user to selectthe type of fish caught. The zone (185) is shown and a series of optionsfor fish associated with the zone are available to choose from for theuser. The user can select an option (e.g., Coho Silver Fin Clipped) fora fish that is caught. As previously noted, the mobile app can alsoprovide other options for a user to provide information about the fishcaught, including the capture of an image of the fish for lateridentification.

Once the fish is selected, an option 76 is provided at FIG. 9 to allowthe user to input information about the size of the fish (e.g., a lengthin inches). After such information has been entered by the user, themobile app, at FIG. 10, allows the user the option of recording thecatch with the specific information provided (i.e., specific type offish, size of fish, GRC location for catch, date and/or time of catch,etc.). In response to the user selecting “Yes”, the catch is recordedand applied to the punch card associated with the user's fishing licenseregistration. It is noted that, once a catch is recorded, it cannot berevised or altered since it is recorded with the state's electronicdatabase via the mobile app 70. The mobile app 70 is then returned tothe main menu 72 (FIG. 8).

The mobile app 70 allows the user to view his or her electronic punchcard 80, as shown in FIG. 12. The punch card 80 shows all of the catchesmade by the user (including number of harvested animals) and recordedwith the punch card stored by the mobile app 70 (and/or optionallyuploaded to a server 20). In addition, as depicted in FIG. 13, themobile app 70 can further be configured to provide additionalinformation associated with the user's punch card 80, such as an alertregarding the expiration date for the punch card as well as informationrelating to the user's punch card approaching a maximum number of a typeof fish allowed to be caught by the user for the punch card registrationperiod (e.g., a notice indicating the user has “only 5 punches left forSalmon Steel Head” as shown in FIG. 13). The mobile app 70 can furtherbe prompted to provide automated messages indicating when a punch cardis about to expire, has expired and/or has no punches left for aparticular type of fish, where the prompt can be displayed as depictedin FIG. 14. When a punch card 80 expires, the mobile app 70 provides adisplay prompt 86 at FIG. 15 allowing a user to record the punch cardwith the state (e.g., by uploaded the electronic punch card informationto a server associated with the state of Oregon, such as a server 20).When the user selects to record the punch card 80, a display message 88is provided in FIG. 16 indicating when recordation takes place andproviding the user with the option (e.g., by providing an email address)for where an electronic copy (e.g., a PDF copy) of the recordation is tobe provided.

The mobile app 70 can also be configured to provide a user option (e.g.,via a prompt selection at the main menu of the mobile app) to viewrecorded data about the user's registered catches as well as totalregistered catches by all users of the system, where recorded data canbe presented in any suitable manner that is useful to the user. Forexample, a user might select a particular GRC location (e.g., 185), andthe mobile app 70 can provide a display table 90 as shown in FIG. 17 ofcatch data for a particular time period, such as month-to-month data fora particular year, of the number of particular types of fish caught atthe selected GRC. Other types of data can also be provided to the uservia the mobile app 70. For example, if the user selects a particulartype of fish, the mobile app 70 can provide data regarding GRC locationsat which the particular type of fish has been registered as caught aswell as a breakdown of catch number over selected time periods (e.g., ona month-to-month basis, a day-to-day basis, etc.) for such GC locations.As depicted in FIG. 18, a display map 92 can also be provided via themobile app 70 which shows locations via icons 94 on the map 92 whereparticular fish are caught. The map can be updated in real time toprovide a focused view of where and what types of fish are caught at anygiven time.

The mobile app embodiments of the present invention can further beassociated with an existing user's fishing license, for example, basedupon a bar code and/or or a QR (quick response) code printed on theuser's license registration card or other issued paperwork provided by astate or other government agency. In an example embodiment, a user whomay not have the mobile app on his or her smart phone may scan a barcode or QR on his or her printed license registration, where thescanning action might prompt the smart phone to visit an Internetwebsite location that allows the user to download the mobile app to hisor her smart phone. In scenarios in which the user already has themobile app loaded on his or her smart phone, scanning of the bar code orQR will link or associate the user's license registration with themobile app for purposes of registering numbers and/or types of catches,punch cards and/or utilizing other features of the mobile app.

Thus, the present invention facilitates a number of advantages foridentifying and recording animal harvests for the government sector(managing wildlife ecology), the private (commercial) sector and foreducational purposes.

While the invention has been described in detail and with reference tospecific embodiments thereof, it will be apparent to one skilled in theart that various changes and modifications can be made therein withoutdeparting from the spirit and scope thereof. Thus, it is intended thatthe present invention covers the modifications and variations of thisinvention provided they come within the scope of the appended claims andtheir equivalents.

What is claimed:
 1. One or more computer readable storage media encodedwith software comprising computer executable instructions and when thesoftware is executed operable to: facilitate entry by a user into afirst electronic device an indication of an animal harvest; generateinformation associated with the animal harvest, wherein the generatedinformation comprises an automatic identification of an animal species,and at least one of a geographic location indicating where the animalharvest occurred and a date of the animal harvest, and the automaticidentification of the animal species comprises automatically assigningan animal code to the animal harvest based upon an image of the animalharvested that is captured by a camera of the first electronic device;upload harvest data from the first electronic device to a secondelectronic device, wherein the harvest data includes at least some ofthe generated information associated with the animal harvest; andassociate the uploaded harvest data with a hunting or fishing license ofthe user of the first electronic device, wherein the associating theuploaded harvest data with the hunting or fishing license of the user ofthe first electronic device includes associating the uploaded harvestdata with a number of harvested animals by the user and furthercomparing the number of harvested animals by the user with a maximumnumber of animals allowed to be harvested by the user based upon anumber of animals the user has registered to harvest via the hunting orfishing license of the user.
 2. The one or more computer readablestorage media of claim 1, wherein the first electronic device comprisesa mobile device, and the second electronic device comprises a serverthat stores the harvest data in a database including harvest dataassociated with other animal harvests.
 3. The one or more computerreadable storage media of claim 2, wherein the mobile device comprises amobile phone, and the instructions are further operable to: obtainGlobal Positioning System (GPS) information associated with the mobilephone.
 4. The one or more computer readable storage media of claim 3,wherein the GPS information corresponds with the geographic locationindicating where the animal harvest occurred, and the instructions arefurther operable to: based upon the obtained GPS information, determinea geographic reference code (GRC) associated with the geographiclocation indicating where the animal harvest occurred; wherein theharvest data uploaded to the server includes the GRC.
 5. The one or morecomputer readable storage media of claim 4, wherein the instructions arefurther operable to: based upon the GRC, provide an alert messageregarding a specific animal species for the GRC.
 6. The one or morecomputer readable storage media of claim 4, wherein the instructions arefurther operable to: facilitate downloading of information to the mobiledevice comprising records of harvested animals at any GRC selected bythe user via the mobile device.
 7. The one or more computer readablestorage media of claim 1, wherein the associating the uploaded harvestdata with the hunting or fishing license of the user of the firstelectronic device includes associating the uploaded harvest data with apunch card for the user that compares a number of harvested animals bythe user with a maximum number of animals allowed to be harvested asindicated by the punch card.
 8. The one or more computer readablestorage media of claim 1, wherein a portion of the generated informationassociated with the animal harvest is generated by the second electronicdevice.
 9. A computer-implemented method for recording an animalharvest, the method comprising: receiving by user entry into a firstelectronic device an indication of an animal harvest; generatinginformation associated with the animal harvest, wherein the generatedinformation comprises an automatic identification of an animal species,and at least one of a geographic location indicating where the animalharvest occurred and a date of the animal harvest, and the automaticidentification of the animal species comprises automatically assigningan animal code to the animal harvest based upon an image of the animalharvested that is captured by a camera of the first electronic device;uploading harvest data from the first electronic device to a secondelectronic device, wherein the harvest data includes at least some ofthe generated information associated with the animal harvest; andassociating the uploaded harvest data with a hunting or fishing licenseof the user of the first electronic device, wherein the associating theuploaded harvest data with the hunting or fishing license of the user ofthe first electronic device includes associating the uploaded harvestdata with a number of harvested animals by the user and furthercomparing the number of harvested animals by the user with a maximumnumber of animals allowed to be harvested by the user based upon anumber of animals the user has registered to harvest via the hunting orfishing license of the user.
 10. The method of claim 9, wherein thefirst electronic device comprises a mobile device, and the secondelectronic device comprises a server that stores the harvest data in adatabase including harvest data associated with other animal harvests.11. The method of claim 10, wherein the mobile device comprises a mobilephone, and the method further comprises: obtaining Global PositioningSystem (GPS) information associated with the mobile phone.
 12. Themethod of claim 11, wherein the GPS information corresponds with thegeographic location indicating where the animal harvest occurred, andthe method further comprises: based upon the obtained GPS information,determine a geographic reference code (GRC) associated with thegeographic location indicating where the animal harvest occurred,wherein the harvest data uploaded to the server includes the GRC. 13.The method of claim 12, wherein the method further comprises: based uponthe GRC, providing an alert message to the mobile device regarding aspecific animal species for the GRC.
 14. The method of claim 12, whereinthe method further comprises: downloading information to the mobiledevice comprising records of harvested animals at any GRC selected bythe user via the mobile device.
 15. The method of claim 9, wherein theassociating the uploaded harvest data with the hunting or fishinglicense of the user of the first electronic device includes associatingthe uploaded harvest data with a punch card for the user that compares anumber of harvested animals by the user with a maximum number of animalsallowed to be harvested as indicated by the punch card.
 16. The methodof claim 9, wherein a portion of the generated information associatedwith the animal harvest is generated by the second electronic device.17. One or more computer readable storage media encoded with softwarecomprising computer executable instructions and when the software isexecuted operable to: facilitate entry by a user into a first electronicdevice information associated with an animal harvest, wherein theinformation comprises an animal species selected from a list of animalspecies provided within a graphical user interface (GUI) displayed bythe first electronic device, wherein the selected animal species isassociated with an animal code; obtain Global Positioning System (GPS)information from the first electronic device; based upon the GPSinformation, obtain a geographic reference code (GRC) representing ageographic location indicating where the animal harvest occurred and theanimal code for the harvested animal; upload harvest data from the firstelectronic device operated by the user to a second electronic deviceoperated by an entity other than the user, wherein the harvest dataincludes the information entered by the user as well as the GRC and theanimal code, and the second electronic device collects harvest data fromthe user and from other electronic devices operated by other users; andassociate the uploaded harvest data with a hunting or fishing license ofthe user of the first electronic device, wherein the associating theuploaded harvest data with the hunting or fishing license of the user ofthe first electronic device includes associating the uploaded harvestdata with a number of harvested animals by the user and furthercomparing the number of harvested animals by the user with a maximumnumber of animals allowed to be harvested by the user based upon anumber of animals the user has registered to harvest via the user'slicense.